5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
- Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 3-1: Overview of APPX Processes

Process Control Files


A process can operate on the data that is contained in any number of files through use of ILF routines, but it can automatically manage only one file. This automatically managed file is referred to as the process control file (PCF) and it applies to input, output, update, query, and inquiry processes. For example, the PCF for a customer maintenance input process is the customer file. APPX automatically reads the PCF while executing the process. In addition, for input processes only, APPX automatically writes, rewrites, and deletes records in the PCF as a function of process execution.

If you want to automatically maintain more than one file, such as entering sales order header information and line item information together, create a separate process for each file and link them together. For example, invoke the line item process as an automatic childfrom the sales order header process. APPX also provides for updating the child PCF for automatic children of input processes to ensure relational integrity. See the following sections, Automatic and Optional Child Invocation and Process Lineage, for additional information on parent and child processes.

A PCF is optional for input and output processes. An input process that does not include a PCF will execute once, and then automatically end (as opposed to executing once for every record). Output processes that do not specify a PCF can be used, for example, to produce standardized page headings and page footers.

Update, query, and inquiry processes must have a process control file. Menu, job, status, and subroutine processes cannot have a PCF.

Application Design Manual                                         "Powered by Appx Software"

252

©2006 By APPX Software, Inc. All Rights Reserved